Embabel Agent Documentation/com.embabel.agent.systemone

Package-level declarations

Types

@ApiStatus.Experimental

How an endpoint exposes System One over HTTP. The protocol's own layout is STANDARD: decisions at /v1/systemone, the model name sent as given, the response body as the System One response, and models listed at /v1/models. A hosting API that puts the model in the path or wraps responses in its own envelope overrides the methods that differ.

SystemOneEndpoint

@ApiStatus.Experimental

class SystemOneEndpoint constructor(val provider: String, val baseUri: URI, val connectTimeout: Duration = DEFAULT_TIMEOUT, val readTimeout: Duration = DEFAULT_TIMEOUT, val maxResponseBytes: Int = DEFAULT_MAX_RESPONSE_BYTES, val requestIdHeader: String? = null, val binding: SystemOneBinding = SystemOneBinding.STANDARD)

Where a System One endpoint lives and how to talk to it.

SystemOneModelFactory

@ApiStatus.Experimental

open class SystemOneModelFactory constructor(endpoint: SystemOneEndpoint, val defaultModel: String, apiKey: Supplier<String?>, restClientBuilder: <Error class: unknown class>? = null, observationRegistry: <Error class: unknown class> = ObservationRegistry.NOOP)

Builds decision services for the models on one System One endpoint. Every service the factory builds shares one HTTP client and one key supplier.